<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
	<TITLE></TITLE>
	<META NAME="GENERATOR" CONTENT="StarOffice 6.0  (Solaris Sparc)">
	<META NAME="CREATED" CONTENT="20020529;10474700">
	<META NAME="CHANGEDBY" CONTENT="Charu Chaubal">
	<META NAME="CHANGED" CONTENT="20020529;12534600">
</HEAD>
<BODY LANG="en-US">
<P STYLE="margin-bottom: 0cm">&nbsp; 
</P>
<TABLE WIDTH=100% BORDER=0 CELLPADDING=2 CELLSPACING=0>
	<TR>
		<TD>
			<H2><FONT COLOR="#336699">Using ssh with qrsh</FONT></H2>
		</TD>
	</TR>
</TABLE>
<TABLE WIDTH=100% BORDER=0 CELLPADDING=2 CELLSPACING=0>
	<COL WIDTH=256*>
	<TR>
		<TD WIDTH=100%>
			<P>By default, the Grid Engine command <B>qrsh</B> will use
			standard remote mechanisms (rsh/rlogin) to establish interactive
			sessions. 
			</P>
			<UL>
				<LI><P><B>qrsh</B> by itself will use rlogin</P>
				<LI><P><B>qrsh</B> with a command will establish a rsh
				connection. 
				</P>
			</UL>
			<P>To enable the rsh/rlogin mechanism, special rsh and rlogin
			binaries are provided with Grid Engine (found in
			$SGE_ROOT/utilbin/$ARCH). In addition, to have full accounting and
			process control for interactive jobs, an extended <B>rshd</B>
			comes with Grid&nbsp;Engine. 
			</P>
			<P>As an alternative, Grid Engine can be configured to use <B>ssh</B>
			instead to start interactive jobs. <BR>&nbsp; 
			</P>
			<H3>Advantages of using ssh:</H3>
			<UL>
				<LI><P STYLE="margin-bottom: 0cm">secure connection 
				</P>
				<LI><P STYLE="margin-bottom: 0cm">no need to have suid root
				programs installed (rsh and rlogin have to be suid root)</P>
				<LI><P STYLE="margin-bottom: 0cm">much larger number of running
				sessions per host (not limited by port number &lt; 1024)</P>
				<LI><P STYLE="margin-bottom: 0cm">compression (if lots of data
				pushed through STDIN/STDOUT)</P>
				<LI><P>possibility to attach a tty to remotely executed commands
				(ssh option -t)</P>
			</UL>
			<H3 STYLE="margin-top: 0cm; margin-bottom: 0cm">Disadvantages:</H3>
			<UL>
				<LI><P STYLE="margin-bottom: 0cm">Lack of complete accounting 
				</P>
				<LI><P>lack of process control (reprioritization) 
				</P>
			</UL>
		</TD>
	</TR>
</TABLE>
<H3>How to setup ssh for qrsh:</H3>
<P STYLE="margin-bottom: 0cm">Have ssh working, all keys created ... 
</P>
<P STYLE="margin-bottom: 0cm">Set the parameters rsh_daemon and
rlogin_daemon in your cluster configuration to ssh: 
</P>
<UL>
	<LI><P>rsh_daemon: /usr/sbin/sshd -i</P>
	<LI><P>rlogin_daemon: /usr/sbin/sshd -i 
	</P>
</UL>
<P STYLE="margin-bottom: 0cm">If you have execution hosts with
different architectures that have different paths to ssh, you will
have to make these settings for each execution host individualy
(qconf -mconf host), else you can change the global cluster
configuration (qconf -mconf).</P>
<P>Set the parameters rsh_command and rlogin_command in your cluster
configuration to ssh:</P>
<UL>
	<LI><P>rsh_command&nbsp;&nbsp;&nbsp;&nbsp; /usr/bin/ssh</P>
	<LI><P>rlogin_command&nbsp; /usr/bin/ssh 
	</P>
</UL>
<P>If you have submit hosts with different architectures that have
different paths to ssh, you will have to make these settings for each
submit host individualy (qconf -mconf host), else you can change the
global cluster configuration (qconf -mconf). <BR>&nbsp; <BR>&nbsp; <BR>&nbsp;</P>
</BODY>
</HTML>
